Importing Workflow Containers

The import feature allows a workflow container export file to be imported, creating a workflow container with all resources that were included in the exported container.

1. If the source container had any shared containers that do not already exist in the target site, those containers should be imported first.
2. In the main menu, select Product Design then Export / Import.  The Export / Import page opens.  Go to the Import Workflow Container panel.
3. Complete the necessary information.



Select File to Import	Click the button to open a standard file browser window.  Locate and select the appropriate export file, and the file name and path appear in the field.
Import Mode	A workflow container may be imported to a site where that container already exists. This can be useful for restoring a previous version, or introducing changes that were introduced and tested in another site. This setting controls how the system handles existing resources during the import.
Overwrite	The imported resource replaces the existing resource. For example, if an imported panel has 5 fields, while the existing panel has 20 fields, the panel will have 5 fields after the import.
Merge	The imported resource is merged into the existing resource. For example, an imported panel has 5 new fields and 2 modified fields that already existed, while the existing panel has 20 fields. The 5 fields are added and the 2 modified fields are replaced, so the panel will have 25 fields after the import.
	Note: The merge only works for fields in panels or grids, panels and grids in screens, and screens in workflows. Any other settings, such as responsive disclosure settings, will be overwritten.

4. Click Import Workflow Container to begin the process. 
1. The system validates the import file to confirm that it has not been altered or corrupted.  If the file fails validation, the import stops and an error message is displayed.  A new export file must be generated for import.
2. The system checks that all required security roles are present in the destination system.  If any roles are missing, the import stops and an error message is displayed.  The missing roles must be created before attempting to import the file again.
3. The system checks all included triggers for invalid characters.  If the angle brackets "<" ">" or ampersand "&" characters are found in any triggers, the import stops and an error message is displayed.  The triggers must be corrected in the source system, then a new export file must be generated for import.
4. The data is imported.
5. After the import is complete, the workflow must be published before submissions can be created.

Note: Concurrency issues may occur if other users are working in the system during import.  It is recommended to perform the import during a maintenance window or other downtime.